--------------------------------- W1 W2 Define set of JIRA issues ---------------------------------- W3 W4 W5 W6 Work on issues ---------------------------------- W7 W8 QA, Docs, Packaging ----------------------------------
JBoss OSGi has a release cycle of eight weeks per minor release.
To improve the predictability of releases, the following rules apply:
--------------------------------- W1 W2 Define set of JIRA issues ---------------------------------- W3 W4 W5 W6 Work on issues ---------------------------------- W7 W8 QA, Docs, Packaging ----------------------------------
At the end of W2 there are no more JIRA issues added to a release. Folks have agreed to resolve their respective issues for the given release cycle. There are also no more unassigned issues after W2. Generally, issues are assigned to the person who is supposed to make the next progress step. To minimize conflicts due to overlapping work, progress is indicated using the Start/Stop Progress feature in Jira.
Development continues in trunk of the respective projects until we reach code freeze at the end of W6. At the end of W6 there should only be release or documentation related issues left unresolved.
Then we branch and do the remaining QA related work in that branches. Finally we tag from the QA branches.